home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000153_news@watsun.cc.columbia.edu _Mon Jun 14 12:52:51 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
3KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA27933
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 14 Jun 1999 12:52:51 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id JAA26683
for kermit.misc@watsun.cc.columbia.edu; Mon, 14 Jun 1999 09:41:47 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
Message-ID: <3765058E.C11E22C6@asares.com>
From: "Brian J. Corcoran" <corcoran@asares.com>
Subject: Re: c-kermit output to stderr on linux
Date: Mon, 14 Jun 1999 13:37:19 +0000
Organization: NETPLEX Internet Services - http://www.ntplx.net/
To: kermit.misc@watsun.cc.columbia.edu
Frank da Cruz wrote:
> In article <3762DA05.B12F366E@asares.com>,
> Brian J. Corcoran <corcoran@asares.com> wrote:
> : I'm trying to get a kermit script to output info to stderr with the
> : following command:
> :
> : writeln error {text line}
> :
> : ...but it's still outputing to stdout. Can anybody help with this?
> :
> You're right, it seems to be doing that. Yet the code is using
> "fprintf(stderr,...)" in this case. The reason that the text is not
> actually going to stderr is not obvious.
>
> : If I can't get around the problem this way, is there an easy way to
> : suppress all output from a script, except for certain text?
> :
> WRITE[LN] ERROR should be the way to do it. However, a workaround (for
> UNIX) would be:
>
> open write /dev/tty
>
> and then use WRITE (or WRITELN) FILE.
ah, but that still sends to stdout, rather than stderr, no? I think I've
found a work-around by using a similar concept, using a dedicated named
pipe.
>
>
> : Finally, I've noticed writeln/write-line behaves as write when
> : outputting to stdout (it doesn't include the new-line character). Is
> : this correct behavior?
> :
> No, it's a bug. This will be corrected in the next Beta edit. Hopefully
> by then I will also have figured out why writes to sdterr are not going
> to stderr.
>
> I suspect there must be code somewhere that sends stderr to stdout so
> error messages will come out in sequence with other text, rather than
> butting ahead, but the spot is not obvious. Anyway, if this was done,
> it was probably done for a reason and so fixing it will no doubt break
> something else. I'll try to sort this out in the next Beta.
>
> Thanks for the report.
>
> - Frank
You're welcome. Thanks for the program.
-Brian